POV-Ray : Newsgroups : povray.windows : Suggestions for new POV-Ray Win Features : Re: Suggestions for new POV-Ray Win Features Server Time
28 Jul 2024 14:30:10 EDT (-0400)
  Re: Suggestions for new POV-Ray Win Features  
From: Ronald L  Parker
Date: 30 Oct 1998 22:28:22
Message: <363b8392.7446507@news.povray.org>
On Fri, 30 Oct 1998 22:16:28 -0500, "J. M. Rowlett"
<row### [at] andrewcmuedu> wrote:

>What would be really cool is, if the POV-Ray engine were a COM object, and
>you fed it interfaces to other COM objects to render.  

If you're gonna crosspost, please do it right.  

Here's the relevant part of the new POVLEGAL:

All executables, documentation, modified files and descriptions of
the same must clearly identify themselves as a modified and
unofficial version of POV-Ray. Any attempt to obscure the fact
that the user is running POV-Ray or to obscure that this is an
unofficial version expressly prohibited.

POV-Ray may not be linked into other software either at compile-
time using an object code linker nor at run-time as a DLL,
ActiveX, or other system. Such linkage can tend to blur the end-
user's perception of which program provides which functions and
thus qualifies as an attempt to obscure what is running.

To allow POV-Ray to communicate with outside programs, the official
versions of POV-Ray include several internal communication "hooks" 
for it to call other tasks, often called an Application Programming 
Interface, or API. For example: the generic part of POV-Ray provides
operating system shell-out API commands. The Windows version has a 
GUI-extension API and the ability to replace the text editor.
Modification to these APIs or other officially supported
communication mechanisms to increase functionality beyond that of 
the official version IS EXPRESSLY PROHIBITED.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.